home *** CD-ROM | disk | FTP | other *** search
- Path: crc-news.doc.ca!usenet
- From: Slobodan Celenkovic <slobodan@cs.unh.edu>
- Newsgroups: comp.lang.pascal.delphi.misc,comp.lang.c++
- Subject: Re: C++ with Zapp vs. Delphi
- Date: 18 Jan 1996 23:19:36 GMT
- Organization: The Communications Research Centre
- Message-ID: <4dmki8$6sv@crc-news.doc.ca>
- References: <4coar6$d4n@sun4.bham.ac.uk> <4coip7$69s@news1.usa.pipeline.com> <fRA+w0JfFG5X089yn@oslonett.no> <4dcc4d$6anc@tigger.cc.uic.edu> <4ddke3$5lf@fountain.mindlink.net> <NEWTNews.821822862.4682.keith@keith.gpim.xerox.com> <4dmdcd$6sv@crc-news.doc.ca> <AUSTERN.96Jan18140655@isolde.mti.sgi.com>
- NNTP-Posting-Host: celenkovic.bob.fob003.ic.gc.ca
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 1.1N (Windows; I; 16bit)
-
- austern@isolde.mti.sgi.com (Matt Austern) wrote:
- >
- >Multiple inheritance of implementations can get messy and is rarely
- >needed. Multiple inheritance of interfaces, though, is extremely
- >common; there are lots of designs that are absolutely impossible
- >without it. And even in the case of implementation inheritance:
- >please note that I said "rarely needed", not "never needed".
- >
- >Nor is multiple inheritance a feature that's unique to C++. It's
- >supported by C++, Eiffel, Sather, Java, CLOS, and other languages.
- >(In Java it only applies interfaces.)
- >--
- >Matt Austern
- >SGI: MTI Compilers Group
- >austern@isolde.mti.sgi.com
-
- Ok, lack of expirience. Could you please give me a "typical" example
- where MI is needed for interfaces? Could these things be done using the
- "use" relationship instead of multiple inheritance (have a class use
- other class as data members instead of inheriting from them)?
-
-